This repository has been archived by the owner on Apr 1, 2024. It is now read-only.
Update geoip-conn Zeek package to commit that includes 2020-10-06 db #44
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The geolocation database just got updated, so with #42 having just merged, it's a fine opportunity to create a new Zeek artifact and see how it does with the Brim integration tests now that the logs will be Zeek v.3.2.1 style. Based on a Slack conversation with @nwt it sounds like a few things in the Zeek TSV output may have changed slightly from the way they were before, but I don't have a lot of experience in the degree to which the integration tests rely on very specific formatting of the Zeek events. I guess I'm about to find out.